The present document describes the end-to-end oneM2M functional architecture, including the description of the functional entities and associated reference points.

oneM2M functional architecture focuses on the Service Layer aspects and takes Underlying Network-independent view of the end-to-end services. The Underlying Network is used for the transport of data and potentially for other services.

This present document contains an informative functional role model and normative technical requirements for oneM2M.

The present document defines security solutions applicable within the M2M system.

The present document specifies the protocol translation and mappings between the oneM2M Service layer and management technologies specified by OMA such as OMA DM 1.3, OMA DM 2.0 and OMA LightweightM2M. Note that OMA DM 1.3 and OMA DM 2.0 are collectively called as OMA DM in this document.

The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181i2 Data Model [6].

The present document …

EXAMPLE: The present document provides the necessary adaptions to the endorsed document.

The Scope shall not contain requirements.

The specification will cover the protocol specific part of communication protocol used by oneM2M compliant systems as ‘RESTful HTTP binding’.

The scope of this Work Item includes (not limited to as shown below):

• Binding oneM2M Protocol primitive types to HTTP method
• Binding oneM2M response codes (successful/unsuccessful) to HTTP resopnse codes
• Binding oneM2M RESTful resources to HTTP resources

This specification is depending on Core API protocol specification (TS-0008) for data types.

EXAMPLE: The present document provides the necessary adaptions to the endorsed document.

The Scope shall not contain requirements.

The present document specifies the binding of Mca and Mcc primitives (message flows) onto the MQTT protocol. It specifies

1. How a CSE or AE connects to MQTT
2. How an Originator (CSE or AE) formulates a Request as an MQTT message, and transmits it to its intended Receiver
3. How a Receiver listens for incoming Requests

How that Receiver can formulate and transmit a Response

The Scope shall not contain requirements.

The present document contains a collection of specialist technical terms, definitions and acronyms referenced within the oneM2M specifications.

Having a common collection of definitions and acronyms related to oneM2M documents will:

• ensure that the terminology is used in a consistent manner across oneM2M documents.
• provide a reader with convenient reference for technical terms that are used across multiple documents.

This document provides a tool for further work on oneM2M technical documentation and facilitates their understanding. The definitions and acronyms as given in this document are either externally created and included here, or created internally within oneM2M by the oneM2M TP or its working groups, whenever the need for precise vocabulary is identified or imported from existing documentation.